-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs process updated #274
Docs process updated #274
Conversation
kumare3
commented
Apr 15, 2020
•
edited
Loading
edited
- Better named makefile targets to generate docs
- Also using a pinned version of Flytekit and FlyteIDL for docs
- Added links to go repos documentation
- Fixed the index and introduction page (there was a duplicate)
script/generate_docs.sh
Outdated
@@ -16,13 +16,13 @@ RSTS_DIR=`mktemp -d "${BASEDIR}/rsts_tmp/XXXXXXXXX"` | |||
|
|||
# Copy all rst files to the same place | |||
cp -R rsts/* ${RSTS_DIR} | |||
cp -R _rsts/* ${RSTS_DIR} | |||
#cp -R _rsts/* ${RSTS_DIR} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't remember, what does this do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think we need this, good catch, added back
+1 with one comment. approving, not sure if you want to change it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but the github workflow doesn't push to gh-pages automatically right? we still need to do that separately.
Right, that should be a follow up PR, I have something in progress, mind helping? |
yes ofc.
…On Thu, Apr 16, 2020 at 11:24 AM Ketan Umare ***@***.***> wrote:
but the github workflow doesn't push to gh-pages automatically right? we
still need to do that separately.
Right, that should be a follow up PR, I have something in progress, mind
helping?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#274 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWDFOCVFMXY4VLDJFDYT6LRM5EORANCNFSM4MI4B4MA>
.
|
Signed-off-by: Flyte-Bot <[email protected]> Co-authored-by: flyte-bot <[email protected]>
Specify how resource is cleaned up after successful execution of a k8s pod [Issue](flyteorg#2650) Signed-off-by: SmritiSatyanV [email protected] Signed-off-by: SmritiSatyanV <[email protected]>
Signed-off-by: Flyte-Bot <[email protected]> Co-authored-by: flyte-bot <[email protected]>
Specify how resource is cleaned up after successful execution of a k8s pod [Issue](flyteorg#2650) Signed-off-by: SmritiSatyanV [email protected] Signed-off-by: SmritiSatyanV <[email protected]>
## Overview Add some logging to better narrow missing outputs to either admin or propeller paths. In support of https://unionai.atlassian.net/browse/CASE-643 ## Test Plan Unit tests pass + manual inspection ## Rollout Plan (if applicable) Pull over to cloud and deploy admin + propeller ## Upstream Changes Should this change be upstreamed to OSS (flyteorg/flyte)? If so, please check this box for auditing. Note, this is the responsibility of each developer. See [this guide](https://unionai.atlassian.net/wiki/spaces/ENG/pages/447610883/Flyte+-+Union+Cloud+Development+Runbook/#When-are-versions-updated%3F). - [ ] To be upstreamed ## Issue ref CLD-922